-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update iavl with WorkingHash fix #1484
Conversation
protocol/go.mod
Outdated
@@ -432,7 +432,7 @@ replace ( | |||
github.com/cometbft/cometbft => github.com/dydxprotocol/cometbft v0.38.6-0.20240426214049-c8beeeada40a | |||
// Use dYdX fork of Cosmos SDK | |||
github.com/cosmos/cosmos-sdk => github.com/dydxprotocol/cosmos-sdk v0.50.6-0.20240326192503-dd116391188d | |||
github.com/cosmos/iavl => github.com/dydxprotocol/iavl v1.1.1-0.20240408175732-0fca9d69cbc4 | |||
github.com/cosmos/iavl => github.com/dydxprotocol/iavl v1.1.1-0.20240509160433-4cb59900bfb2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question on the underlying iavl fork commit: instead of allowing roy/*
should we specify roy/v1.x.x-fix instead to not push future test commits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't matter. Rule only applies for the branch itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, we don't plan to continue managing the our iavl fork right? We are just using this commit for the WorkingHash fix
The commit dydxprotocol/iavl@4cb59900bfb2 is failing tests. I don't think this is expected. |
@Mergifyio backport release/protocol/v5.x |
✅ Backports have been created
|
(cherry picked from commit 711ae63)
Changelist
WorkingHash was computed incorrectly for trees that are initialized with an InitialVersion. This happens when a new store is introduced in an upgrade. If the store is empty, the hash ends up being the same anyways so the bug only manifests when the store has values at the upgrade height.
See dydxprotocol/iavl@1c8b8e7.
Test Plan
[Describe how this PR was tested (if applicable)]
Author/Reviewer Checklist
state-breaking
label.indexer-postgres-breaking
label.PrepareProposal
orProcessProposal
, manually add the labelproposal-breaking
.feature:[feature-name]
.backport/[branch-name]
.refactor
,chore
,bug
.